Conversation
|
It probably makes sense to have a BCrypt cryptor now to be able to migrate from sha1 or any encryptor from this gem to the "new encryptor" that Devises uses these days. If we agree in this PR, I can do another one to be able to support that rolling or even include in this one. |
|
Merging #20 we can rebase this to merge cleanly. |
sobrinho
force-pushed
the
rolling-encryptor
branch
from
5f7ca3f to
ceb9c5a
Compare
|
@sobrinho This is awesome. Any chance of this making it into a release? Would love to be able to roll from ref: https://www.monterail.com/blog/more-secure-passwords-bcrypt |
sobrinho
force-pushed
the
rolling-encryptor
branch
2 times, most recently
from
ad3c062 to
81fbeb3
Compare
|
PR updated. |
|
@carlosantoniodasilva thoughts? |
|
@sobrinho This is great. Is there any interest in merging this one ? We would love to have this option to move from |
sobrinho
force-pushed
the
rolling-encryptor
branch
from
81fbeb3 to
64a8bb6
Compare
|
PR rebased! The build is broken for another reason on 3.0 rails main and 2.7 rails main. @carlosantoniodasilva feel free to merge this one! |
3 participants
Legacy applications want to migrate from SHA1 to SHA512, for example.
Inspired in what Authlogic has with
transition_from_crypto_providers.